Skip to content

test: use unique cluster name to avoid collisions #1479

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

salasberryfin
Copy link
Contributor

@salasberryfin salasberryfin commented May 26, 2025

/kind failing-test

What this PR does / why we need it:

Use unique cluster names for each test case to prevent name collisions. Reusing cluster resource names creates a situation where the Cluster object may be updated by a different cluster flavor, which may imply that the two definitions are not compatible and a webhook will disallow the change. Thanks @damdo for investigating and getting to the bottom of this.

Which issue(s) this PR fixes:
Fixes #

Special notes for your reviewer:

The same change should be applied to GKE test cases. We can do that in the existing PR #1445, when we're ready to successfully run these tests.

TODOs:

  • squashed commits
  • includes documentation
  • adds unit tests

Release note:

NONE

Copy link

netlify bot commented May 26, 2025

Deploy Preview for kubernetes-sigs-cluster-api-gcp ready!

Name Link
🔨 Latest commit f17b52a
🔍 Latest deploy log https://app.netlify.com/projects/kubernetes-sigs-cluster-api-gcp/deploys/68346a881e9974000808317f
😎 Deploy Preview https://deploy-preview-1479--kubernetes-sigs-cluster-api-gcp.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels May 26, 2025
@k8s-ci-robot k8s-ci-robot requested review from damdo and dims May 26, 2025 09:00
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: salasberryfin

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 26, 2025
@salasberryfin salasberryfin force-pushed the fix-clusterclass-e2e-errors branch from 38d4c5c to dd33d16 Compare May 26, 2025 09:51
@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label May 26, 2025
@salasberryfin salasberryfin force-pushed the fix-clusterclass-e2e-errors branch from dd33d16 to f17b52a Compare May 26, 2025 13:20
@salasberryfin
Copy link
Contributor Author

/retest

@salasberryfin salasberryfin changed the title WIP: test: use unique cluster name to avoid collisions test: use unique cluster name to avoid collisions May 27, 2025
@k8s-ci-robot k8s-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label May 27, 2025
Copy link
Member

@damdo damdo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It works!
Thanks Carlos

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label May 29, 2025
@k8s-ci-robot k8s-ci-robot merged commit a369469 into kubernetes-sigs:main May 29, 2025
20 checks passed
@k8s-ci-robot k8s-ci-robot added this to the v1.1.0 milestone May 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants